Food description processing methods and apparatuses

ABSTRACT

Disclosed embodiments include apparatuses, methods and storage media associated with modifying a food record database. The method comprises receiving a plurality of food records from a plurality of sources, each of the plurality of food records comprising at least a food record description, the plurality of sources including (i) at least one non-user entity that is an owner of a third party food database and (ii) users of the food record database. The method further comprises receiving search requests from users, and returning one or more top search results from the food record database in response. The method also comprises determining a score for a particular food record identified by the top search results, wherein the score is calculated based at least in part on one of: a number of times the particular food record has been included in the top search results of the search requests or a number of times the particular food record has been logged.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/747,229, filed Jan. 20, 2020, which is a continuation of U.S. patentapplication Ser. No. 14/480,401, filed Sep. 8, 2014, both also entitled“Food Description Processing Methods and Apparatuses,” the entirecontents of which are incorporated by reference herein.

FIELD

The present disclosure relates to the field of data processing. Moreparticularly, the present disclosure relates to food descriptionprocessing.

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Unless otherwiseindicated herein, the materials described in this section are not priorart to the claims in this application and are not admitted to be priorart by inclusion in this section.

Historically, when gathering data from multiple sources either thevarious sources may need to be aware of any formatting requirementsthere may be for the data, or the entity performing the gathering mayneed to know how the data is formatted in the individual sources. Ifneither of the above is the case, the entity gathering the data may belimited as to how the data may be able to be utilized. Such a scenariomay be exacerbated by the collection of data from users where any numberof users may enter data and the users may not know, or really even care,what format the data is to be entered in. So long as the data serves theindividual user's purpose, the user may be satisfied. Specifically, inscenarios where the data may concern descriptions of foods, includingnutritional information, the data entered by various users may varydramatically. As a result, an entity wishing to utilize the user entereddata may have to manually modify individual user entries to conform tothe desired data format or may have to live with the format of the dataas the user entered it.

SUMMARY

In at least one embodiment, a system comprises database having aplurality of food records including (i) one or more official foodrecords comprising data obtained from a third party food database, and(ii) one or more food records comprising data provided by users of thesystem, wherein each of the food records comprises at least adescription of a food item. The system further comprises one or moreprocessors and a food data processing engine. When operated by the oneor more processors, the food data processing engine amends at least oneof the food records in the database by causing the system to standardizethe at least one food item description of the at least one food record,and determine a score associated with the at least one food record,wherein the score is calculated based at least in part on one of: anumber of times the at least one food record has been logged or a numberof times the at least one food record appeared in recent searches of thedatabase. The food data processing engine further causes the system tocreate a new food record comprising the standardized description,associate the new food record to a cluster of food records, the clustercomprising a plurality of food records identified as being descriptiveof a same food item, and designate the new food record as a candidaterecord representative of the cluster based on a result of thedetermination of the score.

In at least one embodiment, a method of modifying a food record databaseis disclosed. The method comprises receiving a plurality of food recordsfrom a plurality of sources, each of the plurality of food recordscomprising at least a food record description, the plurality of sourcesincluding (i) at least one non-user entity that is an owner of a thirdparty food database, and (ii) users of the food record database. Themethod further comprises receiving search requests from the users of thefood record database, and returning one or more top search results fromthe food record database in response to each of the search requests,wherein the one or more top search results identify a limited number offood records in the database that have food record descriptions whichare most closely associated to a food description entered in the searchrequest. The method also comprises determining a score for a particularfood record identified by the top search results, wherein the score iscalculated based at least in part on one of: a number of times theparticular food record has been included in the top search results ofthe search requests or a number of times the particular food record hasbeen logged. When the score is greater than a predetermined threshold,amend the particular food record to include a designation of theparticular food record as a candidate record representative of a clusterof food records in the database.

In yet another embodiment of the disclosure, a non-transitorycomputer-readable medium comprising one or more instructions, which whenexecuted by the processor, causes the processor to receive a request tosearch a food database, the database comprising a plurality of foodrecords, the food records received from a plurality of sources, each ofthe plurality of food records comprising at least a name and nutritiondata relating to one of a plurality of foods, wherein the plurality ofsources comprises (i) at least one non-user entity that is an owner of athird party food database, and (ii) a plurality of users. In response tothe request, the system accesses the database to identify one or morefood records that are most closely associated with the search requestbased at least in part on a level of similarity between words entered inthe search request and the respective food record names. The systemfurther determines a score for each of the identified one or more foodrecords, wherein the score is calculated based at least in part on oneof: a number of times each of the identified one or more food recordshas been logged or a number of times each of the identified one or morefood records has appeared in prior searches of the database. Thereafter,the system returns a list of the identified one or more food records,the list including at least one designator configured to indicate aparticular one of the identified one or more food records which wasdetermined to have a highest score.

The above described features and advantages, as well as others, willbecome more readily apparent to those of ordinary skill in the art byreference to the following detailed description and accompanyingdrawings. While it would be desirable to provide food descriptionprocessing methods and apparatuses that provide one or more of these orother advantageous features as may be apparent to those reviewing thisdisclosure, the teachings disclosed herein extend to those embodimentswhich fall within the scope of the appended claims, regardless ofwhether they include or accomplish one or more of the advantages orfeatures mentioned herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings.

FIG. 1 illustrates a fitness management system suitable for practicingthe present disclosure, according to the various embodiments.

FIG. 2 illustrates example operation flow of processing a fooddescription, according to the various embodiments.

FIG. 3 illustrates an example operation flow of storing a standardizedand normalized food description, according to various embodiments.

FIG. 4 illustrates another example operation flow of storing astandardized and normalized food description, according to variousembodiments.

FIG. 5 illustrates example cluster records, according to the variousembodiments.

FIG. 6 illustrates example food records, according to variousembodiments.

FIG. 7 illustrates an example computing system suitable for use as aninteractive messaging computing device or a portable client device,according to various embodiments.

FIG. 8 illustrates an example storage medium having instructions tocause a computing device to practice aspects of interactive messaging,according to various embodiments.

DESCRIPTION

Disclosed embodiments include apparatuses, methods and storage mediaassociated with food description processing.

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Aspects of the disclosure are disclosed in the accompanying description.Alternate embodiments of the present disclosure and their equivalentsmay be devised without parting from the spirit or scope of the presentdisclosure. It should be noted that like elements disclosed below areindicated by like reference numbers in the drawings.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

For the purposes of the present disclosure, the phrase “A and/or B”means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

Referring now to FIG. 1, wherein a fitness management system, accordingto the various embodiments, is illustrated. As shown, fitness managementsystem (FMS) 100 may include any number of client devices (e.g., clientdevice 102) and one or more server(s) 104 coupled with each other.Server(s) 104 may host a fitness management application (FMA) 112,including a number of databases, e.g., food and beverages database 114and user database 116, configured in accordance with the teachings ofthe present disclosure. Whereas client device 102 may include a clientside agent 122 of FMA 112 configured to access and interact with FMA112, to enable a user of the client device 102, among other things, todevelop a fitness plan that may include a nutritional, or food andbeverage, budget, and monitor the progress towards meeting the fitnessplan. For example, a user may develop a fitness plan including a caloricbudget designating a number of calories the user would like to consumein a day. For those attempting to lose weight the designated number ofcalories may be a maximum number the user may like to stay below, while,for those looking to gain weight, the designated number of calories maybe a minimum number of calories the user may like to stay above. In someembodiments, the user may be able to further designate the nutritionalsources for these calories. For example, if a user would like to limitthe user's caloric intake from fat, the user may designate a maximumbudget of the user's calories from fat. As another example, if the useris looking to gain or maintain muscle mass the user may designate aminimum budget of the user's caloric intake that should come fromproteins.

Once such a fitness plan is developed, the user may utilize client sideagent 122, in conjunction with FMA 112, to monitor the user's intake offoods and/or beverages. This may be accomplished by the user enteringindividual food and/or beverage items that the user consumes along withquantities of these food and/or beverage items consumed. In someinstances the food and/or beverage item may already have a food recordin food and beverages database 114. In such instances, the user maymerely select the food and/or beverage item from a list of food and/orbeverage items and then enter quantity consumed. FMA agent 122, inconjunction with FMA 112, may then be configured to incorporate theconsumption of the food and/or beverage item into the user's nutritionalbudget based upon a description of the food item in the food record ofthe food and beverages database 114. Such a food record may includenutritional information, such as that discussed below. In some instancesthe food and/or beverage item may not have an existing record, or theuser may not be able to find the appropriate food record for the foodand/or beverage item. In such instances, the user may enter theinformation that the user knows about the food including a foodidentifier, brand name, country of origin, a description including anynutritional information the user knows, and any additional descriptionthe user would like to enter for the food. Such information may then beincorporated into the user's nutritional budget as well as incorporatedinto food and beverages database 114.

In embodiments, server(s) 104, except for FMA 112 and databases 114-116,may be any one of a number of computer servers, real or virtual, knownin the art, including, but not limited to, servers available from DellComputing of Austin, Tex. or Hewlett Packard of Palo Alto, Calif. Inembodiments, FMA 112 may include food data pre-processing engine 124,hereinafter referred to simply as “pre-processing engine 124.” Whereasfood & beverages database 114 may include food and beverage items,including a description of the food and beverage items that may includenutrient information associated with the food and beverage items, aswell as recipes and ingredient items. Examples of nutrient informationmay include, but are not limited to, amounts of protein; sugar; variousfats, including trans-fat, saturated fat, etc.; sodium; carbohydrates,both complex and simple; calcium, various vitamins and/or calories perserving. In some embodiments, server(s) 104 may represent a cloudcomputing environment where each of FMA 112, pre-processing engine 124,food and beverages database 114, and user database 116 may reside,individually or in any combination, on servers, real or virtual, of thecloud computing environment.

As discussed above, in some embodiments, a user may enter informationregarding a food and/or beverage item to be incorporated into the user'snutritional budget. This user entered information may also beincorporated into food and beverages database 114 and may enable foodand beverages database 114 to grow through user entered information.Such user entered information may be referred to as crowd-sourcedinformation. A problem with this user entered information is that it maynot be formatted in a manner consistent with other food recordscontained within food and beverages database 114. In some embodiments,such inconsistently entered information may result in a number ofduplicate food records for the same food and/or beverage item. Inaddition, the inconsistency of the information may make it difficult fora user to find a specific food and/or beverage item that is containedwithin the database, and, as a result, the user may enter duplicate, ornearly duplicate, information and lose any efficiency that would begained by utilizing the previously entered information. To combat suchinconsistently entered food and/or beverage information, pre-processingengine 124 may be configured to process the user entered food and/orbeverage information to standardize and/or normalize the informationbefore entry of the information as a food record in food and beveragesdatabase 114.

In embodiments, client device 102 may be any one of a number ofstationary or portable electronic devices known in the art, including,but not limited to, desktop computers (e.g. those available from DellComputing of Austin, Tex.), smartphones, computing tablets, laptopcomputers, electronic readers, personal digital assistants, and soforth, such as Galaxy S4 from Samsung Electronics of Seoul, Korea, oriPad from Apple Computer of Cupertino, Calif. In embodiments, one ormore portable computing devices 102 may be a wearable computing device,e.g., a smart watch, smart eyeglasses (e.g., Google Glass from Google ofMountain View, Calif.), and so forth. In embodiments, FMA agent 122 maybe a web-based application configured to operate in a generic browser,such as Internet Explorer, available from Microsoft Corp., of Redmond,Wash., or Safari from Apple Computer of Cupertino, Calif. In otherembodiments, FMA agent 122 may be a stand-alone client side application,e.g., a mobile app configured to run on a smartphone such as, forexample, a mobile app available through the App Store from AppleComputer of Cupertino, Calif.

In embodiments, client device 102 and server(s) 104 may becommunicatively coupled with one another via communication link 106 overone or more wired and/or wireless, private and/or public networks,including the Internet. Client device 102 and server(s) 104 may beconfigured with the appropriate networking communication interfaces. Anexample of a wired communication interface may include, but is notlimited to, Ethernet, while examples of wireless communicationinterfaces may include, but are not limited to, near field communication(NFC), Bluetooth, WiFi, 4G or 5G LTE. In between the communicationinterfaces of client devices 102 and server(s) 104 may be any number ofgateways, routers, switches, based stations, and so forth.

Hereinafter, for ease of description, including the claims, the term“food” will be used to mean “food and/or beverage,” unless the contextclearly indicates otherwise.

FIG. 2 illustrates an example process flow for processing a descriptionof a food item by pre-processing engine 124 of FIG. 1, in accordancewith various embodiments of the present disclosure. The process flow maybegin at block 202 where the description of the food item may bereceived by the pre-processing engine. Such a description may bereceived by the pre-processing engine, for example, from FMA agent 122of client device 102 of FIG. 1 via communication link 106 of FIG. 1. Asdiscussed above in reference to FIG. 1, the description may be enteredby a user of computing device 102, for example, to describe a foodand/or beverage item that the user consumed to be incorporated into afitness plan the user developed.

In some embodiments, at block 204 the pre-processing engine may analyzethe description to determine whether the description contains a brandname. This may be accomplished by the pre-processing engine tokenizingthe description, including any brand name the description may contain.As used herein, tokenizing may refer to the process of dividing the textof the description into smaller components, or tokens, to be processed.The tokens may be individual characters, words, groups of words (e.g.,every three words), or groups of characters (e.g., every fivecharacters).

Once the description has been tokenized it may be processed by thepre-processing engine to standardize the description. This may beaccomplished, for example, by the pre-processing engine removing specialcharacters, spaces, etc. from the description. A list of normalizedbrand names, which may be stored, for example, as a table in the foodand beverages database, may then be retrieved by the pre-processingengine which may then tokenize and standardize the list of normalizedbrand names in the same manner as the description. Standardizing thelist of normalized brand names in the same manner as the description mayenable a more accurate search of the description for the normalizedbrand names. In some embodiments, each brand name in the list ofnormalized brand names may also have commonly used non-normalized brandnames associated therewith. For example, if the normalized brand name isMcDonald's, then the non-normalized brand names associated therewith maybe Mcdonalds, McDonalds, McDonald, etc. In such embodiments, thenon-normalized brand names may also be standardized in the same manneras the normalized brand names.

Once the description, normalized brand names, and, in some embodiments,the non-normalized brand names associated with the normalized brandnames, have been tokenized and standardized, the individual tokens ofthe normalized and non-normalized brand names may be searched todetermine whether the description contains a brand name (e.g., through ahashing process). If an exact match to one of the normalized ornon-normalized brand names is not found, then, in some embodiments, theprocess may proceed to determine if a brand name within a threshold ofsimilarity is contained within the description. This procedure may alsoresult in the correction of brand names that may be misspelled by theuser. For example, misspelled brand “P. F. Chnag's” will fall within thethreshold of similarity of the brand “P. F. Chang's”, and may becorrected in the process. The threshold of similarity may, in someembodiments, be based on a Damerau-Levenshtein distance analysis whichmay provide a count of the number of operations it would take totransform one or more tokens of the description into one of thenormalized or non-normalized brand names. Such a count may commonly bereferred to as a distance, or modified edit distance, between the one ormore tokens and the normalized or non-normalized brand name. If thedistance between the normalized or non-normalized brand names and theone or more tokens of the description are within a predefined distancefrom one another, then the one or more tokens may be determined to bewithin a threshold of similarity to the normalized or the non-normalizedbrand name. In such an instance, the determination in block 204 may bein the affirmative and the process may proceed to block 206. In otherembodiments, such an analysis may be accomplished using a Jaccard index,or Jaccard coefficient analysis, which may take the one or more tokensand determine a measure of the overlap. An example of such an analysisis discussed further below in reference to FIG. 3. If a brand name isnot found within the description then the process may proceed to block212.

At block 206, the one or more tokens may be extracted from thedescription. In some embodiments, this extraction may include theextraction of one or more additional tokens either before or after theone or more tokens of the brand name. For example, if the descriptionstates “sandwich from McDonalds” the “from” contained in the descriptionmay be extracted in addition to the brand name. In some embodiments,such additional tokens may be automatically extracted by designatingthat a token leading into a brand name and/or a token following a brandname are to be extracted along with the brand name. In otherembodiments, the tokens before and after the brand name may be analyzedto determine if the word is a common leading or trailing word (e.g., apreposition) to be extracted. Such common leading or trailing words maybe contained in a list of leading and/or trailing words stored, forexample, in a table of the food and beverages database. In someembodiments, the normalized brand name that is within a threshold ofsimilarity may be associated with the description to be recorded as thebrand name for the description being processed (e.g., brand name of foodrecord 1 of FIG. 6).

At block 208, in some embodiments, the brand name extracted from thedescription may be replaced with a descriptive name. For example, if thenormalized brand name is “French's” the extracted brand name may bereplaced with a descriptive name, such as mustard. Such a descriptivename may be associated with the normalized brand name via the table ofnormalized brand names, for example, discussed above. It will beappreciated, that block 208 may be optional and, as a result, may beomitted in some embodiments. At block 210, the normalized brand name maybe stored, for example as part of a food record in food and beveragesdatabase 114 of FIG. 1, after which the processing may proceed to block212. It will be appreciated that, in some embodiments, the procedures ofblocks 204-210 may be optional and, as a result, may be omitted from theprocessing performed by the pre-processing engine.

At block 212, pre-processing engine may process the description togenerate a standardized and/or normalized description for the food item.This may be accomplished by first standardizing the description of thefood item for processing. Such standardization may begin by cleaning thedescription. Such a cleaning may include the removal of stop wordsdesignated, for example, by a list of stop words contained within atable of the food and beverages database. The cleaning may also includethe removal of punctuation or special characters from the description.In addition, the cleaning process may include the removal of anyunnecessary delimiters, such as, for example, removal of consecutivespaces. In some embodiments, the cleaning may also include removal of“bad” keywords that may be defined, for example, in a table of badkeywords stored in the food and beverages database. Such bad keywordsmay be for example, profanities, vulgarities, etc.

Once the description has undergone the above cleaning process, thedescription may be further standardized and/or normalized by removingany usernames from the description. As used herein, standardized mayrefer to standardization of a single instance of a descriptionindependent of any other description instances, while normalized mayrefer to normalization of a single instance with respect to otherdescription instances contained with a set of description instances(e.g., with respect to the clusters discussed below or with respect toother records within the food and beverages database). This may beaccomplished by utilizing a user database (e.g., user database 116 ofFIG. 1) to construct a username dictionary to utilize in analyzing thedescription for any usernames. Such an analysis and removal may beperformed in a similar manner to the analysis and removal of brand namesdescribed above in reference to FIG. 2. In some embodiments, thestandardization may also include the analysis and removal of any countrynames contained within the description. Again, the removal of thecountry names may be performed in a similar manner to the analysis andremoval of brand names described above. In some embodiments, any countryname contained within the description may be stored in a country fieldof a food record for the description. In some embodiments, thecapitalization may also be standardized as part of the standardizationprocess. Standardizing the capitalization may involve, for example,converting all capital letters to lowercase. At block 214 pre-processingengine may cause the standardized and/or normalized description of thefood item to be stored in a fitness management system, such as FMS 100of FIG. 1. In embodiments, this may include storage of the descriptionof the food item, the brand name of the food item, the country of thefood item, and/or any other pertinent information with respect to thefood item, as a food record in the food and beverages database.

FIG. 3 illustrates an example process flow 300 store a standardizedand/or normalized food description, in accordance with variousembodiments of the present disclosure. In some embodiments, when storinga description of a food item, it may be desirable to determine whether aduplicate, or nearly duplicate, description for the food item alreadyexists. This may prevent duplicate, or nearly duplicate, descriptions ofthe same food item from taking up unnecessary space in a storagemechanism, such as food and beverages database 114 of FIG. 1, inaddition to reducing the amount of noise contained within food itemsearch results that may be caused by duplicate, or near duplicate,records for the same food items. Process 300 depicts an illustrativeprocess that may prevent or limit the storage of duplicate, or nearduplicate, descriptions of the same food item. Such a process may becarried out as part of block 216 of FIG. 2.

Process 300 may begin at block 302 where pre-processing engine maydetermine whether an existing food record contains an exact duplicatedescription for the same food item. This may be accomplished by takingthe standardized and/or normalized description and constructing n-grams(or k-shingles) from the standardized or normalized description. As usedherein, n-grams may be a contiguous sequence of n items from thedescription. The items may be phonemes, syllables, letters, words, etc.K-shingles on the other hand, may refer to k contiguous subsequences ofthe n-grams. For example, consider a food item ‘A’ where thestandardized description of food item A is “Chicken sandwich with whiteonions and peppers.” A three shingle set for food item A may be{[Chicken, sandwich, with], [sandwich, with, white], [with, white,onions], [onions, and, peppers]}. If a food record already exists thatcontains an exact duplicate description, (e.g., has the exact sameshingle set as food item A) then the process may proceed to block 312where process 300 may end and the description being stored may bediscarded. If an existing food record does not contain an exactduplicate description, then the process may proceed to block 304.

At block 304, pre-processing engine may determine whether an existingfood record contains a description for a food item that is within athreshold of similarity of the description of the food item beingprocessed. The threshold of similarity may, as described above inreference to the brand name analysis, be based on a Damerau-Levenshteindistance analysis which may provide a count of the number of operationsit would take to transform the description being processed into adescription of an existing food record. Such a count may commonly bereferred to as a distance between the description being processed andthe description of the existing food record. If the distance between thedescription being processed and the description of the existing foodrecord are within a predefined distance from one another, then thedescription being processed and the description of the existing foodrecord may be determined to be within a threshold of similarity to oneanother. In such an instance, the determination in block 304 may be inthe affirmative and the process may proceed to block 308. In otherembodiments, this may be accomplished utilizing a Jaccard index, orJaccard coefficient analysis, which may be depicted by the equation

${J\left( {A,B} \right)} = {\frac{{A\bigcap B}}{{A\bigcup B}}.}$

where A may be the shingle set of A and B may be the shingle set of B.In such an embodiment, returning to the above example, consider a fooditem ‘B’ where the standardized description of food item B is “Chickensandwich with onions and peppers.” A three shingle set for food item Bmay be {[Chicken, sandwich, with], [sandwich, with, onion], [with,onions, and], [onions, and, peppers]}. Utilizing the Jaccard coefficientanalysis yields

${J\left( {A,B} \right)} = {\frac{{A\bigcap B}}{{A\bigcup B}} = {\frac{3}{6} = {{.5}.}}}$

In addition, the Damerau-Levenshtein distance between food item A andfood item B would be 5, because the two descriptions are identical otherthan the word “white” which would attribute 5 characters to theDamerau-Levenshtein distance. If the threshold of similarity is, forexample, 0.4, for the Jaccard coefficient example, or, for example 8,for the Damerau-Levenshtein example, then the determination of block 304may be in the affirmative and the processing may proceed to block 308.If, however, the determination of block 304 is in the negative, then theprocess may proceed to block 306 where the description, along withbrand, country, etc. may be stored into a new food record of the foodand beverages database. After the description of the food item beingprocessed is stored at block 306, the process may proceed to block 312where the process may end.

At block 308 pre-processing engine may make a determination as towhether the description for the food item being processed containsadditional information not contained within the description of theexisting record. For example, a user may have previously entered adescription omitting the amount of sodium contained within a serving ofthe food item and the description being processed may contain thisinformation. If the description for the food item being processed doesnot contain additional information, then the process may proceed toblock 312 where the process may end. If, however, the description forthe food item being processed does contain additional information, thenthe process may proceed to block 310 where the pre-processing engine mayeither merge the additional information into the description containedwithin the existing record or replace the existing record with thedescription of the food item being processed. The description beingprocessed and the description of the existing record may be merged, forinstance, by incorporating the additional information contained withinthe description being processed into the description of the existingrecord. Returning to the example above, such a merge may be accomplishedby adding the amount of sodium contained within the description beingprocessed to the description of the existing record. Once procedure 310is complete, the process may proceed to block 312 where the process mayend.

FIG. 4 illustrates another example process flow 400 of storing astandardized and normalized food description, according to variousembodiments. Process flow 400 differs from process flow 300 of FIG. 3 inthat records containing similar descriptions for the same food item may,in some embodiments, be organized into clusters (e.g., the clustersdiscussed below in reference to FIG. 5). In such embodiments, exactduplicates of existing food records may still be discarded, however, anew food description that is within a threshold of similarity to adescription of an existing food record may be added to a clusterassociated with the existing food record. Such an embodiment isdiscussed in further detail below.

Process 400 may begin at block 402 where pre-processing engine maydetermine whether an existing food record contains an exact duplicatedescription for the same food item. This may be accomplished in asimilar manner to that described above in reference to process 302 ofFIG. 3. If a food record already exists that contains an exact duplicatedescription, then the process may proceed to block 416 where process 400may end and the description being stored may be discarded. If anexisting food record does not contain an exact duplicate description,then the process may proceed to block 404.

At block 404, pre-processing engine may determine whether an existingfood record contains a description for a food item that is within athreshold of similarity of the description of the food item beingprocessed. As discussed above in reference to FIG. 3, the threshold ofsimilarity may, in some embodiments, be based on a Damerau-Levenshteindistance analysis which may provide a count of the number of operationsit would take to transform the description being processed into adescription of an existing food record. Such a count may commonly bereferred to as a distance between the description being processed andthe description of the existing food record being processed. If thedistance between the description being processed and the description ofthe existing food record are within a predefined distance from oneanother, then the description being processed and the description of theexisting food record may be determined to be within a threshold ofsimilarity one another. In such an instance, the determination in block404 may be in the affirmative and the process may proceed to block 408.If, however, the determination of block 404 is in the negative, then theprocess may proceed to block 406 where the description, along withbrand, country, etc. may be stored into a new food record of the foodand beverages database. After the description of the food item beingprocessed is stored at block 406, the process may proceed to block 416where the process may end.

At block 408, a score for the description being processed may bedetermined. Such a score may be based on any factor that may be utilizedto prioritize the description being processed. For example, the scoremay be based on additional information contained within the descriptionbeing processed; the number of times the description being processed hasbeen logged by a user; a measure of reliability of the source of thedescription (e.g., if the description were acquired from the FDA); thenumber of times the description being processed has appeared in the topresults of recent searches, etc. Once a score for the description hasbeen determined the process may proceed to block 410.

At block 410, a determination may be made as to whether the scorecalculated at block 408 is greater than the score of the currentcandidate record for the cluster associated with the existing recordhaving a description within a threshold of similarity with thedescription being processed. If the score of the description beingprocessed is less than, or equal to, the score of the current candidaterecord, then the process may proceed to block 412 where the descriptionbeing processed, along with country, brand name, etc. may be added as anew record to the cluster. If, however the score of the descriptionbeing processed is greater than the score of the current candidaterecord, then the process may proceed to block 414 where the descriptionbeing processed, along with country, brand name, etc. may be added as anew record to the cluster and the new record may be set as the newcandidate record for the cluster. Once the processing at block 414 hasconcluded, the process may proceed to block 416 where the process mayend.

FIG. 5 illustrates example cluster records 502 for clusters 1-5 inaccordance with various embodiments of the present disclosure. Asdepicted, each cluster record may include a number of food identifiersto identify the records associated with the cluster. Each cluster mayalso include a candidate identifier that may identify the currentcandidate record associated with the cluster. In addition, the clusterrecord may, in some embodiments, include a score of the currentcandidate, such as the score discussed above in reference to FIG. 4. Inaddition, the cluster may, in some embodiments, include a count for theaverage shingle set of the various food records associated with thecluster.

FIG. 6 illustrates example food records 1-6, in accordance with variousembodiments of the present disclosure. As depicted, each food record 602may include a brand name associated with the food record. In someembodiments, the food record may also include a cluster identifier thatmay identify the cluster to which the food record is associated. In someembodiments, the food record may also indicate a score associated withthe food record, such as the score described above in reference to FIG.4. Finally, each food record may include a description and or a shingleset associated with the food record, such as the shingle set discussedin reference to FIG. 4, above.

Referring now to FIG. 7, wherein an example computer suitable for use asserver(s) 104 or client device 102 of FIG. 1, in accordance with variousembodiments, is illustrated. As shown, computer 700 may include one ormore processors or processor cores 702, and system memory 704. For thepurpose of this application, including the claims, the terms “processor”and “processor cores” may be considered synonymous, unless the contextclearly requires otherwise. Additionally, computer 700 may include massstorage devices 706 (such as diskette, hard drive, compact disc readonly memory (CD-ROM) and so forth), input/output devices 708 (such asdisplay, keyboard, cursor control and so forth) and communicationinterfaces 710 (such as network interface cards, modems and so forth).The elements may be coupled to each other via system bus 712, which mayrepresent one or more buses. In the case of multiple buses, the busesmay be bridged by one or more bus bridges (not shown).

Each of these elements may perform its conventional functions known inthe art. In particular, when used as server(s) 104, system memory 704and mass storage devices 706 may be employed to store a working copy anda permanent copy of the programming instructions implementing theoperations associated with fitness management application 112 andpre-processing engine 124 of FIG. 1, above, collectively referred to ascomputational logic 722. The various elements may be implemented byassembler instructions supported by processor(s) 702 or high-levellanguages, such as, for example, C, that can be compiled into suchinstructions.

The permanent copy of the programming instructions may be placed intopermanent storage devices 706 in the factory, or in the field, through,for example, a distribution medium (not shown), such as a compact disc(CD), or through communication interface 710 (from a distribution server(not shown)). That is, one or more distribution media having animplementation of the agent program may be employed to distribute theagent and program various computing devices.

The number, capability and/or capacity of these elements 710-712 mayvary, depending on whether computer 700 is used as server(s) 104 orclient device 102. When used as client device 102, computing device 700may be a smartphone, computing tablet, e-reader, ultrabook, or laptop.Otherwise, the constitutions of elements 710-712 are known, andaccordingly will not be further described.

FIG. 8 illustrates an example computer-readable non-transitory storagemedium having instructions configured to practice all or selected onesof the operations associated with earlier described fitness managementapplication 112 and/or preprocessing engine 124 of FIG. 1, in accordancewith various embodiments. As illustrated, non-transitorycomputer-readable storage medium 802 may include a number of programminginstructions 804. Programming instructions 804 may be configured toenable a device, e.g., computer 800, in response to execution of theprogramming instructions, to perform, e.g., various operations of theprocesses described above in reference to FIGS. 1-4, e.g., but notlimited to, the operations associated with pre-processing engine 124. Inalternate embodiments, programming instructions 804 may be disposed onmultiple computer-readable non-transitory storage media 802 instead. Inalternate embodiments, programming instructions 804 may be disposed oncomputer-readable transitory media 802, such as, signals.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the disclosed embodiments ofthe disclosed device and associated methods without departing from thespirit or scope of the disclosure. Thus, it is intended that the presentdisclosure covers the modifications and variations of the embodimentsdisclosed above provided that the modifications and variations comewithin the scope of any claims and their equivalents.

What is claimed is:
 1. A system comprising: a database comprising aplurality of food records including (i) one or more official foodrecords comprising data obtained from a third party food database and(ii) one or more food records comprising data provided by users of thesystem, wherein each of the food records comprises at least adescription of a food item; one or more processors; and a food dataprocessing engine, which, when operated by the one or more processors,amends at least one of the food records in the database by causing thesystem to: standardize the at least one food item description of the atleast one food record; determine a score associated with the at leastone food record, wherein the score is calculated based at least in parton one of: a number of times the at least one food record has beenlogged or a number of times the at least one food record appeared inrecent searches of the database; create a new food record comprising thestandardized description; associate the new food record to a cluster offood records, the cluster comprising a plurality of food recordsidentified as being descriptive of a same food item; and designate thenew food record as a candidate record representative of the clusterbased on a result of the determination of the score.
 2. The system ofclaim 1, wherein the score associated with the at least one food recordis calculated based in part on a score for the standardized food itemdescription of the food record.
 3. The system of claim 2, wherein thescore for the standardized food item description is based in part on atleast one of: a measure of reliability of a source of the description orinformation contained within the description.
 4. The system of claim 1,wherein the food data processing engine is further configured to causethe system to display a list of food records from the cluster of foodrecords.
 5. The system of claim 4, wherein the food data processingengine is further configured to associate an identifier with thecandidate record and display the identifier with the candidate record inthe list of food records.
 6. The system of claim 4, wherein the fooddata processing engine is further configured to move the candidaterecord to a top of the list of food records.
 7. The system of claim 1,wherein standardizing the at least one food item description includes:division of the food item description into a plurality of componentwords; elimination of unnecessary ones of the plurality of componentwords; and standardization of remaining ones of the plurality ofcomponent words via removal of special characters or features therefrom.8. The system of claim 7, wherein at least one of the component wordscomprises a brand name and the standardization comprises causing thedescription to match a description provided by a brand owner.
 9. Thesystem of claim 1, wherein the third party database is provided by atleast one of a government agency, a consumer product company, and a fooddata organization, and wherein the one or more food records comprisingdata provided by users of the system are crowd-sourced food records. 10.The system of claim 1, wherein food includes beverage such that theplurality of food records include beverage records.
 11. A method ofmodifying a food record database, the method comprising: receiving aplurality of food records from a plurality of sources, each of theplurality of food records comprising at least a food record description,the plurality of sources including (i) at least one non-user entity thatis an owner of a third party food database; and (ii) users of the foodrecord database; receiving search requests from the users of the foodrecord database; returning one or more top search results from the foodrecord database in response to each of the search requests, wherein theone or more top search results identify a limited number of food recordsin the database that have food record descriptions which are mostclosely associated to a food description entered in the search request;determining a score for a particular food record identified by the topsearch results, wherein the score is calculated based at least in parton one of: a number of times the particular food record has beenincluded in the top search results of the search requests or a number oftimes the particular food record has been logged; and when the score isgreater than a predetermined threshold, amend the particular food recordto include a designation of the particular food record as a candidaterecord representative of a cluster of food records in the database. 12.The method of claim 11, wherein the score is further calculated based inpart on a score for a standardized food item description of theparticular food record.
 13. The method of claim 12, wherein the scorefor the standardized food item description is based in part on at leastone of: a measure of reliability of a source of the description orinformation contained within the description.
 14. The method of claim11, further comprising displaying the designation with the candidaterecord in a list of food records and moving the candidate record to atop of the list of food records.
 15. The method of claim 11, wherein thenon-user entity is at least one of a government agency, a consumerproduct company, and a food data organization.
 16. A non-transitorycomputer-readable medium comprising one or more instructions, which whenexecuted by the processor, causes the processor to: receive a request tosearch a food database, the database comprising a plurality of foodrecords, the food records received from a plurality of sources, each ofthe plurality of food records comprising at least a name and nutritiondata relating to one of a plurality of foods, wherein the plurality ofsources comprises (i) a plurality of users of a health tracking system,and (ii) at least one owner of a third party food database that is anon-user of the health tracking system; in response to the request,access the database to identify one or more food records that are mostclosely associated with the search request based at least in part on alevel of similarity between words entered in the search request and therespective food record names; determine a score for each of theidentified one or more food records, wherein the score is calculatedbased at least in part on one of: a number of times each of theidentified one or more food records has been logged or a number of timeseach of the identified one or more food records has appeared in priorsearches of the database; and returning a list of the identified one ormore food records, the list including at least one designator configuredto indicate a particular one of the identified one or more food recordswhich was determined to have a highest score.
 17. The computer-readablemedium of claim 16, wherein the one or more instructions are furtherconfigured to, when executed by the processor, cause the processor toamend the particular one of the identified one or more food records toinclude the designator.
 18. The computer-readable medium of claim 16,wherein the score for each of the identified one or more food records iscalculated based in part on a score for a standardized food itemdescription of the food record.
 19. The computer-readable medium ofclaim 16, wherein the score for each of the identified one or more foodrecords is based in part on at least one of: a measure of reliability ofa source of the description or information contained within thedescription.
 20. The computer-readable medium of claim 16 wherein the atleast one owner of the third party database is at least one of agovernment agency, a consumer product company, and a food dataorganization.